[% setvar title The Perl 6 Development Log %]
<div id="archive-notice">
    <h3>This file is part of the Perl 6 Archive</h3>
    <p>To see what is currently happening visit <a href="http://www.perl6.org/">http://www.perl6.org/</a></p>
</div>
<div class='pod'>
<a name='TITLE'></a><h1>TITLE</h1>
<p>The Perl 6 Development Log</p>
<a name='VERSION'></a><h1>VERSION</h1>
<pre>  Maintainer: Simon Cozens &lt;<a href='mailto:simon@brecon.co.uk'>simon@brecon.co.uk</a>&gt;
  Date: Sep 24 2000
  Mailing List: <a href='mailto:perl6-internals@perl.org'>perl6-internals@perl.org</a>
  Number: 281
  Version: 1
  Status: Developing</pre>
<a name='ABSTRACT'></a><h1>ABSTRACT</h1>
<p>Proposes a way of creating a specification for Perl 6 internals and
getting a development log and internals documentation for free.</p>
<a name='DESCRIPTION'></a><h1>DESCRIPTION</h1>
<p>Perl 5's internals are a scary place, and it's probable that Perl 6's
are going to be at least mildly scary as well. Since we're planning to
have a lot of people working on the guts, we need a lot of people to
know how they work, and this means good guts documentation. Here's how
we do it.</p>
<p>Dan, or whoever, produces the specifications for the internals, and this
gets hammered out right down to the function level. We split this thing
up into the files the functions will go into, and we have a document per
file.</p>
<p>As people implement the functions, they add to the file, noting who they
are, what they've done, when they did it and what approach they took.
Some of this can probably be automated. As people make changes to the
functions in the future, they also add to the log.</p>
<p>This means we've got a document for each file which explains what the
function's supposed to do, how it fits in to the grand scheme of things,
why it's coded as it is, and how it's developed.</p>
<a name='IMPLEMENTATION'></a><h1>IMPLEMENTATION</h1>
<p>JFDI.</p>
<a name='REFERENCES'></a><h1>REFERENCES</h1>
<p>None.</p>
</div>
